Skip to content

fix(ci): downgrade upload-artifact to v4.5.0 to fix glob resolver - #27

Merged
williaby merged 1 commit into
mainfrom
fix/sbom-upload-artifact-sha
Apr 10, 2026
Merged

williaby merged 1 commit into
mainfrom
fix/sbom-upload-artifact-sha

Conversation

@williaby

@williaby williaby commented Apr 10, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

actions/upload-artifact v4.6.2 (ea165f8d) has a broken glob resolver that fails to match files via absolute paths on current GitHub-hosted runners. The SBOM file is confirmed present at $GITHUB_WORKSPACE/sbom-runtime.json (17,768 bytes, verified by the diagnostic step added in #26) but the upload step reports "No files were found with the provided path".

Downgrading to v4.5.0 (6f51ac03), which uses @actions/glob v0.5.x with a working resolver.

Changes

Evidence

From run 24250664647 (PR #26, after anchoring to $GITHUB_WORKSPACE):

Verify SBOM files before upload:
  354173  20 -rw-r--r-- 1 runner runner 17768 Apr 10 17:01
    /home/runner/work/.claude/.claude/sbom-runtime.json

Upload SBOM artifacts:
  ##[error] No files were found with the provided path:
    /home/runner/work/.claude/.claude/sbom-*.json

File exists, path matches, glob fails — consistent with a resolver bug in v4.6.2.

Note on version label

The current SHA was annotated # v4.6.2 (correct — it does resolve to v4.6.2, not v3). The glob breakage is a regression in that release, not a version mismatch.

Testing

  • Trigger the SBOM workflow and confirm the upload step finds sbom-runtime.json
  • Confirm scan-runtime and license-compliance jobs receive the artifact and complete

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Updated build workflow artifact upload configuration.

actions/upload-artifact v4.6.2 (ea165f8d) has a broken glob resolver
that fails to match files via absolute paths on current GitHub-hosted
runners. The file exists at $GITHUB_WORKSPACE/sbom-runtime.json (17768
bytes confirmed by the Verify step in run 24250664647) but the upload
step reports "No files were found with the provided path".

Pinning to v4.5.0 (6f51ac03) which uses @actions/glob v0.5.x with the
working resolver. The download-artifact steps are already at v4.3.0
(d3f86a10) from the previous fix and remain compatible.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
@williaby
williaby merged commit f61402a into main Apr 10, 2026
3 of 4 checks passed
@coderabbitai

coderabbitai Bot commented Apr 10, 2026 •

Copy link
Copy Markdown

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 65dd50dc-03fa-4469-ad81-af04eb5e8bd9

📥 Commits

Reviewing files that changed from the base of the PR and between 400193f and 5a06760.

📒 Files selected for processing (1)
  • .github/workflows/python-sbom.yml

📝 Walkthrough

Walkthrough

A GitHub Actions workflow configuration was updated by changing the pinned version of the actions/upload-artifact action in the SBOM build pipeline from v4.6.2 to v4.5.0, with all other artifact upload parameters remaining intact.

Changes

Cohort / File(s) Summary
Workflow Configuration
.github/workflows/python-sbom.yml
Downgraded actions/upload-artifact action pin from commit ea165f8d65b6e75b540449e92b4886f43607fa02 (v4.6.2) to commit 6f51ac03b9356f520e9adb1b1b7802705f340c2b (v4.5.0) in the "Upload SBOM artifacts" step.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Poem

🐰 A version shift, not quite a bound,
From four point six to five we've found,
The artifact path stays the same,
A minor pinning tweak to fame! 📌

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/sbom-upload-artifact-sha

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant